Skip to main content

This is a new service – your feedback will help us to improve it.

Uttlesford District Council

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

8 Individual, 5 Areas

reference
1/77/53-591
name
8 Individual, 5 Areas
tree-preservation-order

undefined

1/77/53-591
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((0.211470 51.858306,0.211148 51.858304,0.211017 51.858310,0.210903 51.858176,0.210807 51.858057,0.210766 51.857998,0.210728 51.857948,0.210631 51.857808,0.210590 51.857709,0.210560 51.857610,0.210546 51.857377,0.210548 51.857292,0.210562 51.857199,0.210578 51.857134,0.210596 51.857079,0.210640 51.857067,0.210701 51.857098,0.210729 51.857114,0.210848 51.857155,0.210914 51.857175,0.210951 51.857208,0.210926 51.857214,0.210884 51.857237,0.210861 51.857252,0.210845 51.857266,0.210842 51.857269,0.210838 51.857278,0.210838 51.857281,0.210861 51.857296,0.210870 51.857305,0.210874 51.857337,0.210872 51.857351,0.210864 51.857370,0.210849 51.857367,0.210846 51.857370,0.210838 51.857396,0.210839 51.857415,0.210846 51.857433,0.210855 51.857445,0.210869 51.857456,0.210872 51.857460,0.210903 51.857478,0.210996 51.857515,0.211104 51.857550,0.211211 51.857582,0.211352 51.857613,0.211387 51.857616,0.211393 51.857618,0.211407 51.857618,0.211420 51.857611,0.211695 51.857673,0.211683 51.857679,0.211674 51.857686,0.211670 51.857710,0.211635 51.857789,0.211605 51.857873,0.211553 51.858046,0.211526 51.858153,0.211506 51.858221,0.211470 51.858306)))
point
POINT (0.211055 51.857785)
notes
entry-date
1978-04-11
start-date
1978-04-11
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Uttlesford District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL